This is the name of the selected item.


This is the icon that corresponds to the selected item.


Provides a description to help identify and manage the selected item. An administrator can enter a new description, up to 500 characters long.


Provides a space to enter the maximum time (in seconds) that transactions can remain active before they timeout. Transactions that remain active beyond the transaction timeout period are automatically aborted by the system. If you set this value to 0, transactions will never timeout. You should set this to a value greater than 0 to avoid the risk of having the system hang in the event of a distributed deadlock. The default value for the computer-level setting is 60 seconds; the default value for the component-level setting (which overrides the computer-level setting when enabled) is 0.


Provides a space for an administrator to enter a remote server name used for application proxies exported from this server. If this property is blank, the computer network name will be used.


An administrator selects this to designate the local system as the default coordinator. A space is also provided for an administrator to enter the name of the remote system that will serve as the default coordinator.


Provides a space for an administrator to enter the name of the system that will serve as the remote system. An administrator can also click Select to display and select from a list of computers on the network.


An administrator selects this to display a list of all computers on the network and to select a computer from the list.


An administrator selects this to specify the network protocol used to communicate with a remote commit coordinator.


Information box for the MS DTC log file.


Provides a space for an administrator to enter the current path of the MS DTC log file. An administrator will first need to stop MS DTC, specify a new location for the log file, and then click Reset. Alternatively, you may click Browse to select the location dynamically.


An administrator clicks this to browse for a location for the MS DTC log file.


Provides a space for an administrator to enter the size in megabytes of the MS DTC log file. An administrator will need to first stop MS DTC, specify a new size for the log file, and click Reset.


An administrator clicks this to reinitialize the MS DTC log file by deleting the existing file from the location specified in the Location box. The specified drive, directory, and capacity setting control the location and size of the log file. Before deleting an existing log file, you must ensure that there are no transactions in the in-doubt state. This will ensure that the parent MS DTC for the transaction is accessible. You can confirm the current state using the Component Services administrative tool's Transaction List window.


Displays the current status of the MS DTC service, indicating whether it is currently running, and if so the time at which it was last started.


An administrator clicks this to start the MS DTC service.


An administrator selects this to specify that DCOM is available for all COM+ applications installed on this computer, making it possible for this computer to exchange calls with applications on other computers.


An administrator selects this to specify that DCOM communication is available over the Internet through a firewall for all COM+ applications installed on this computer.


Lists default levels at which client and server applications should verify one another's identities during calls. An administrator uses this box to set the system-wide default used when neither the client nor the server specifies their own authentication levels. The settings, from lowest to highest security, are as follows:

•	Default. The default authentication level for the security package is used.

•	None. No authentication occurs.

•	Connect. Authentication occurs only when the connection is made.

•	Call. Authenticates at the beginning of every call.

•	Packet. Authenticates and verifies that all call data is received.

•	Packet Integrity. Authenticates and verifies that none of the data has been modified in transit.

•	Packet Privacy. Authenticates and encrypts the packet, including the data and the sender's identity and signature.


Lists default levels of authority that a client on this computer can grant to a server application to perform processing tasks on its behalf. An administrator uses this box to set the system-wide default used when the client application has not programmatically set its own impersonation level. The settings are as follows:

•	Anonymous. The client is anonymous to the server application. The server can impersonate the client, but the impersonation token does not contain any information about the client.

•	Identify. The server application can obtain the client's identity, and can impersonate the client to do ACL checks.

•	Impersonate. The server application can impersonate the client while acting on its behalf, but with restrictions: The server can access resources on the same computer as the client. If the server is on the same computer as the client, it can access network resources as the client. If the server is on a computer different from the client, it can only access resources that are on the same computer as the server.

•	Delegate. The server application can impersonate the client while acting on its behalf, whether or not on the same computer as the client. During impersonation, all of the client's credentials can be passed to any number of computers. The Windows NT LAN Manager security support provider does not support this level.


An administrator selects this to specify authentication of distributed reference count calls on this computer. When enabled, reference tracking helps prevent clients from releasing objects too early. No matter how many times a particular client calls Release, the object and stubs will still exist as long as another client has a reference to the object. Enabling reference tracking can also decrease performance.


An administrator clicks this to choose user accounts and groups that are allowed or denied permission by default to access applications on this computer. This system-wide default applies to COM applications installed on this computer, but it is used only when an application does not provide its own access permissions. This setting does not affect COM+ applications.


An administrator clicks this to choose user accounts and groups that are allowed or denied permission to start applications on this computer. This system-wide default applies to COM applications installed on the computer, but it is used only when an application does not provide its own launch permissions. This setting does not affect COM+ applications.


Lists the set of network protocols available to COM on this computer. Using this dialog box, an administrator can add or remove network protocols, change the priority in which they will be used, and configure protocol properties.


An administrator clicks this to add a network protocol that will be available for use by COM on this computer.


An administrator clicks this to remove the selected network protocol from the list of those available to COM on this computer.


An administrator clicks this to move the selected network protocol to a higher priority position in the list. The ordering of the protocols reflects the priority in which they will be used, with the top protocol having first priority.


An administrator clicks this to move the selected network protocol to a lower priority position in the list. The ordering of the protocols reflects the priority in which they will be used, with the top protocol having first priority.


An administrator clicks this to configure the properties for the selected protocol. This option may not be available for all protocols.


Lists the ports and/or port ranges, which form the set of ports for dynamic assignment in the Internet or intranet partition. The standard DCOM port range runs from 1024 through 65,535.


An administrator clicks this to add a port or range of ports to the Port Ranges list. The port identifier must be a number within the range of 0 through 65,535.


An administrator clicks this to remove the selected port or range of ports from the Port Ranges list.


An administrator clicks this to remove all ports and port ranges from the Port Ranges list.


An administrator selects one of these to specify whether the ports in the Ports Ranges list are assigned to the Internet (public access) or intranet (private access).


An administrator selects one of these to specify whether dynamic port allocation occurs by default on the Internet or intranet port range partition.


Displays the application identifier of the selected COM+ application. This number is a GUID (globally unique identifier) generated automatically when you created the COM+ application. An administrator can use the Application ID to identify particular versions of the application on a computer.


Lists the values a developer uses to set the level at which this COM+ application should verify the identity of its clients. The settings, from lowest to highest security, are as follows:

•	None. No authentication occurs.

•	Connect. Authentication occurs only when the connection is made.

•	Call. Authenticates at the beginning of every call.

•	Packet. Authenticates and verifies that all call data is received.

•	Packet Integrity. Authenticates and verifies that none of the data has been modified in transit.

•	Packet Privacy. Authenticates and encrypts the packet, including the data and the sender's identity and signature.


Lists the values a developer uses to set the level of authority that the selected COM+ server application, as a client, grants to other applications when they are acting on its behalf. The levels are as follows:

•	Anonymous. The client is anonymous to the server application. The server can impersonate the client, but the impersonation token does not contain any information about the client.

•	Identify. The server application can obtain the client's identity, and can impersonate the client to do ACL checks.

•	Impersonate. The server application can impersonate the client while acting on its behalf, but with restrictions: The server can access resources on the same computer as the client. If the server is on the same computer as the client, it can access network resources as the client. If the server is on a computer different from the client, it can only access resources that are on the same computer as the server.

•	Delegate. The server application can impersonate the client while acting on its behalf, whether or not on the same computer as the client. During impersonation, all of the client's credentials can be passed to any number of computers.


A developer selects this to enable access checks only at the application or process level. No role checking will be done at the component, interface, or method levels. Security information regarding callers into the application (the security call context) will not be available. This setting should not be selected for a library application, as it will mean the application is relying completely on security access checking done by the hosting client process − if that is desired, you should de-select Enforce access checks for this application. (Note that with access checking only at process level, the security property will not be included in the context properties for objects running within the application, which means that security configuration will not affect an object's in-context activation.)


A developer selects this to enable access checks at every level on calls into the application. Role checking will be done at the application or process level (for server applications), and at the component, interface, and method levels for any component that has Enforce component level access checks selected on the component security property tab. Security information regarding callers into the application (the security call context) is available. For library applications, role checking will be performed at the component, interface, and method levels within the application where applicable, and at the process level by the hosting client process. (Note that with access checking at the process and component level, the security property will be included in the context properties for objects running within the application, which means that security configuration can affect an object's in-context activation.)


A developer selects this to enable access checks for the application. When roles have been defined for an application, a caller's role membership is checked on every call into the application. When roles have been assigned at finer levels within the application (at the component, interface, or method levels) membership in these roles may be checked depending on what security level is selected on the application security property tab, and on whether Enforce component level access checks is selected on the component security property tab. For library applications, role checking can be performed only at the component level, so you should not select the process-only security level if you enable access checking.


A developer selects this to specify that the library application's host process performs authentication checks on clients calling the library application.


An administrator selects this to specify that the server process associated with the COM+ application should remain running when there are no outstanding client calls. The application will remain running until it is manually shut down.


An administrator selects this to specify that the server process associated with the COM+ application should shut down automatically after a certain period of inactivity. You can set this period of inactivity by entering the number of minutes.


An administrator selects this to specify that the server process associated with the COM+ application should shut down automatically after a certain period of inactivity. You can set this period of inactivity by entering the number of minutes.


A developer selects this to specify that a server application should be launched in the debugger when it is started, using the debugger command line specified in Debugger path.


Provides a space for a developer to enter the path and command line used for invoking the debugger when Launch in debugger is enabled.


A developer selects this to specify that the application can access up to 3 gigabytes of memory when Windows 2000 Advanced Server has been configured to allow access to more than 2 gigabytes of memory.


A developer selects this to specify that the application cannot be deleted.


A developer selects this to prevent changes made to the application's configuration.


A developer selects this to enable the server application to use a compensating resource manager (CRM). CRM components are only available to the application when this is selected.


An administrator selects this to specify that the application will run under the identity of the user who is currently logged on to the computer (the interactive user). This user's security credentials will be used when the application is authenticated to access resources, such as when it attempts to access files or a database or makes calls to other applications.


An administrator selects this to specify that the application will run under the identity of a specified user account. This user's security credentials will be used when the application is authenticated to access resources, such as when it attempts to access files or a database or makes calls to other applications.


Provides a space for an administrator to enter the account of the user under whose identity the application will run. This can be a user account or a service account you create to run services. If you don't know the user account, click Browse to find it.


Click this button to browse for the desired item.


Provides a space for an administrator to enter the logon password for the specified user account.


Provides a space for an administrator to enter the logon password from the Password box to confirm it.


Developers select this to specify that the COM+ application will run as a library application. A library application runs in the process of the client that creates it, and can only be called by clients located on the same computer. Because library applications run in the client's process, the configurable properties for COM+ library applications are different than for COM+ server applications. If you change an application's activation type, other properties for the application will be reset.


Developers select this to specify that the COM+ application will run as a server application. Server applications run in their own dedicated server process, as opposed to library applications which run in the client's process. The configurable properties for COM+ server applications are different than for COM+ library applications. If you change an application's activation type, other properties for the application will be reset.


Provides a space for an administrator to enter the remote server name used by the application proxy. An application proxy serves to direct client calls to a COM+ server application installed on the remote computer.


An administrator selects this to export the selected COM+ application as an application proxy. When installed on a client computer, the application proxy enables remote access to the server application on this machine.


An administrator selects this to export the selected COM+ application as a server application. The server application can then be installed on another computer using the Component Services administrative tool.


An administrator enters the full path and filename for the server application or application proxy file to be created. The component (.dll) files for the application will also be copied into the specified directory.


An administrator selects this to export user identities along with the selected COM+ application's roles. The application's roles indicate logical groups of users allowed to access components, interfaces, and methods. With the Component Services administrative tool, you can also add users to roles after installing the server application on another computer.


An administrator selects this to export the application proxy as an .msi file. The .msi file contains registration information that allows the client to remotely access a server application using DCOM. The .msi file can be installed on any Windows-based client using Windows Installer.


An administrator selects this to export the application proxy as an .apx file. The .apx file, along with other files (which may include type libraries and marshaling information), contains registration information that allows the client to remotely access a server application using DCOM and the COM+ queued components service. These files are installed on a computer using the Component Services administrative tool.


Developers select this to specify that an application is eligible to receive messages.


Developers select this to enable a queue listener that reads messages from the input queue and creates server-side components.


The name of the selected component.


Displays the path of the DLL containing the class and interface definitions for the component.


Displays the unique class identifier (CLSID) of the selected component.


Displays the unique application identifier of the application in which the component is installed.


A developer selects this to specify an alternative component (exception class) for the player to activate and playback before being routed to the dead letter queue. Using the alternative component implies that the exception class should implement the same queued interfaces as those implemented by the original queued component.


Developers select this to eliminate transaction-related overhead for objects that will never access a resource manager. This attribute simulates the transactional behavior of an unconfigured component — a COM component that has not been installed in a COM+ application.


Developers select this to prevent an object from participating in a transaction, regardless of the transactional status of its caller. Declaring this value guarantees that an object will not vote in its caller's transaction or begin a transaction of its own. Not supported is the default value for all components.


Developers select this to allow an object to participate in a transaction if one exists. Declaring this value causes an object to share in its caller's transaction, but prevents it from initiating a transaction of its own.


Developers select this to specify that all objects created from the component will be transactional. This is the preferred setting for a object that performs resource activities, because it guarantees transaction protection for those activities.


Developers select this to require that an object be the root of a new transaction, regardless of the transactional status of the caller. COM+ automatically initiates a new transaction, which is distinct from the caller's transaction.


A developer selects this to specify that the component should use its own transaction timeout value instead of the value set for the computer. If you do not set a value for the component, any transaction initiated by this component will use the timeout value set on the computer properties option tab. If this check box is selected, you can enter a value (in seconds) in the Transaction Timeout box.


Developers select this to specify that synchronization is disabled.


Developers select this to specify that the component never supports a synchronization domain.


Developers select this to specify that the component can support a synchronization domain.


Developers select this to specify that the component requires a synchronization domain.


Developers select this to specify that the component requires a new synchronization domain.


Indicates the component's threading model.


A developer selects this to deliver events in parallel to two or more subscribers.


A developer selects this to allow delivery of events to in-process subscribers. For security reasons, the default is to prohibit in-process activation of subscribers.


Specifies the identifier of the publisher from which the subscriber wants to receive events.


A developer selects this to enable access checks at the component, interface, and method levels when roles have been specifically assigned there. Access checks are only carried out if you have also selected both Enforce access checks for this application and the Perform access checks at the process and component level on the application's security property tab.


Lists the roles that have been defined for the application. A check mark next to a role indicates that it is explicitly granted access permission for the item.


A developer selects this to enable object pooling for the component. When pooling is enabled, objects will be recycled and reused, with the number of objects existing at a given time varying between the minimum and maximum pool sizes. New objects are created when none are available in the pool, until the maximum pool size is reached. When the maximum pool size is reached, client requests are queued, waiting no longer than the creation timeout period. Object pooling can only be enabled for components that are written to meet the reuesability requirements for poolable objects.


Provides a space for a developer to enter the minimum number of objects that will be maintained in the pool at any time. Since objects will be automatically created up to the minimum pool size when the application starts, this value can be used to preallocate objects for immediate availability to clients. This value may not be set while the application is running.


Provides a space for a developer to enter the maximum number of objects that can exist in the pool at any time. This can be used to govern the resource utilization by objects in the pool − for instance, if the objects hold database connections, no more connections than the maximum pool size can be open at any given time. This value may not be set while the application is running.


Provides a space for a developer to enter the amount of time (in milliseconds) that the object pool has to provide a requested object. If a request cannot be serviced in the specified amount of time, an error is returned. This value may not be set while the application is running.


A developer selects this to enable object construction for the component. When this is enabled, the Constructor string will be passed to the object on creation, providing parametrized construction of the object if it is written to utilize the constructor string. For instance, if the component holds a generic ODBC connection, an exact DSN can be passed in upon object creation.


Provides a space for a developer to enter a string that will be made available to the object at creation time when object construction is enabled. This provides parametrized construction of the object if it is written to utilize the constructor string. For instance, if the object holds a generic ODBC connection, an exact DSN can be passed in upon object creation. An empty string may be a valid entry.


A developer selects this to specify that the object may be repeatedly deactivated and reactivated just-in-time to handle calls from a client, where the client is unaware that the object was ever deactivated. This provides scaling benefits through efficient utilization of server resources, while freeing clients from having to consider how they use server resources. JIT activation is automatically enabled when transactions are required for the component, and enabling JIT activation forces synchronization to be required for the component.


This option can only be selected after component load balancing has been installed. A developer selects this to specify that when the component load balancing (CLB) service is being used, creation requests for this component will be load balanced across servers in the application cluster. This can yield great scaling benefits when enabled for appropriate components in a COM+ application. Components that use object pooling, for instance, or which make assumptions about having shared data available in-process, should not be load balanced.


A developer selects this to ensure that the object can only be activated within the context of its initial caller. If this is not possible, due to incompatibilities between the context properties of the caller and the configuration of the object, the object will not be activated and the call will fail. You would generally use this setting only where an object cannot support cross-context marshaling, or where you have very stringent performance requirements.


A developer selects this to enable object event reporting and object statistics, such as object call time. You can view object statistics using the status view for the components folder.


Displays the unique identifier of the selected interface.


Lists the roles that have been explicitly granted permission access for the item at a higher level. If a role is displayed as inherited, settings you make for that role in Roles explicitly set for selected item will be ignored.


Specifies the unique identifier for the subscription.


Specifies the unique identifier for the subscriber.


Specifies the EventClass for the subscription.


Specifies the identity of the publisher for which the subscriber will receive events.


Specifies the method name for the subscription.


A developer selects this to enable a subscription so that it appears in a list of active event objects.


Specifies the name of the server containing the list of active event objects.


A developer selects this to make the publisher and subscriber time independent by queuing the publisher's message and later replaying it to the subscriber.


A developer specifies this to provide parameter filtering for each subscription and method invocation. The Filter Criteria string can contain standard relational operators, nested parentheses, and the logical keywords AND, OR, or NOT.


A developer uses this dialog box to edit or add properties for subscribers and publishers.


A developer selects this to edit the information contained for a specific subscriber or publisher.


A developer selects this for purposes of JIT activation. This has the same effect as the method having called SetComplete or SetAbort, indicating the object's work is done and it can be deactivated safely.